|
|
Websydian 3.1b is Websydian 3.1 distributed with the Websydian TransacXML for Java. For further information see here.
Websydian 3.1a is Websydian 3.1 distributed with the Websydian Enterprise WebShop module. For important information about this module please go here.
The Websydian TransacXML developer suite has been enhanced with support for SOAP (Simple Object Access Protocol).
With SOAP and the Websydian patterns to send and receive HTTP requests/responses it is now possible to build advanced Web Services with Plex and Websydian.
For more information please refer to Developing Web Services with Websydian Enterprise TransacXML Developer.
DWA is the interface to use if high scalability and performance is a critical issue. With the distributed architecture the application can easily be deployed to multiple application servers. For more information on DWA please see Distributed Websydian Architecture.
A number of improvements have been applied to the DWA interface since version 3.0. Please see the rest of this section and the section Application Service Controller for details.
In a DWA application the Websydian process (Application Service) is not ended after each request. Since Websydian uses global properties to store information about the input from the user, these properties must be deleted after each request so the next request (which might be initiated by another user) does not have access to the previous input parameters.
When using the EventHandlerWithSignature pattern in v3.0 these global properties was deleted before the request had been processed and this could cause problems for applications trying to read input parameters from the global store rather than using the WebInput variable in the EventHandler function.
This has now been fixed, but please note that there is a problem in the Java variant regarding this issue. Please see Known Problems at www.websydian.com for further information.
The run-time files for the DWA variants have been renamed.
| Old name | New name |
|---|---|
| wsydpka.dll | WsydDwa10.dll |
| wsyd-relay.jar | WsydDwa10.jar |
New parameters have been added to the Websydian Server.
All parameters to the Servlet Websydian Web Server Component must now be specified in a file rather than being configured as servlet parameters.
The Servlet Websydian Web Server Component tried to set the HTTP status code after the response was written. In most servlet engines the call was ignored, but some servlet engines would throw an exception causing the request to fail. This bug has now been fixed.
To set the HTTP status code set the header Status to the wanted HTTP status code.
New packets have been added to the DWA protocol. Therefore it is necessary to re-gen and build the entire application when upgrading and also use the new run-time files.
Due to a bug the server socket was not closed correctly in the DWA run-time (Windows and iSeries) when an Application Server ended. This has now been fixed.
The functions DecodeUrl and HostNameToIp used in the DWA - Windows variant require that the libraries wininet.lib and ws2_32.lib are added to the Gen & Build section.
Due to the introduction of DWA some Websydian objects have been renamed.
| Object type | Old name | New name |
|---|---|---|
| Function | WpkaListener | ApplicationServiceListener |
| Package | PkaObjectsToGenerateAndBuild | DwaObjectsToGenerateAndBuild |
| Package | PkaWinObjectsToGenerateAndBuild | DwaWinObjectsToGenerateAndBuild |
| Field | WpkaServiceName | ApplicationServiceName |
| Field | WpkaInfoText | PacketInfoText |
| Fields | All fields with prefix Wpka | Prefix Wpka removed |
Some bugs in the DocumentTemplateGenerator for the DeckGenerator pattern that prevented the Wml template from being generated correctly have been fixed.
The function EncodeUrl made use of a Windows API to encode URL's. This API did not work correctly in all cases, so now the function traverses the character string and encodes unsafe characters.
When a character field is read from an ODBC data source, some data base engines will pad the field with spaces up to the length of the field. To compensate for this Plex (and Websydian) removes trailing spaces before displaying the field value.
If the database engine does not pad character strings or if the trailing spaces should be sent to the HTML page, a new option has been introduced that disables the removal of trailing spaces.
The script variant now makes use of the HTTP client in the model WsyHttp rather than using the functions in WsyBase.
The functionality has not changed but the library WsyHttp.lib must be included in the generate and build settings.
The source codes scoped under SendHtmlPage has been changed so they are capable of sending binary output. The parameter interface is unchanged.
Websydian no longer uses translation tables to translate character data. Instead information about the code pages to use should be specified in a data area. Please refer to Set up Character Conversion for further details.
Most likely, no changes will be necessary when upgrading a Websydian model from version 3.0 to version 3.1. See the Upgrade Guide to Version 3.1 technical paper for the circumstances in which to do minor modifications when migrating a Websydian model from version 3.0 to 3.1.
Online documentation - Websydian v6.5